chore(renovate): unset minimumReleaseAge for framework#428
Conversation
In the base Renovate config here we're now setting a `minimumReleaseAge`: netlify/renovate-config#109. In this repo however we have a very specific setup for Remix/RR7 framework bumps to provide immediate early warning of incompatibilities with new releases, including unstable releases. So, opt out of `minimumReleaseAge` just for those.
✅ Deploy Preview for angular-runtime-demo ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
…ular-runtime#428) In the base Renovate config here we're now setting a `minimumReleaseAge`: netlify/renovate-config#109. In this repo however we have a very specific setup for Remix/RR7 framework bumps to provide immediate early warning of incompatibilities with new releases, including unstable releases. So, opt out of `minimumReleaseAge` just for those.
In the base Renovate config here we're now setting a
minimumReleaseAge: netlify/renovate-config#109.In this repo however we have a very specific setup for Angular framework bumps to provide immediate early warning of incompatibilities with new releases, including unstable releases. So, opt out of
minimumReleaseAgejust for those.EX-2222